Container for an entire component definition — includes template, settings,
event bindings, property definitions, and compiler + reflection metadata
Container describing the possible variants of a Repeat source
— namely a range expression in PAXEL or a symbolic binding
Container for storing parsed control flow information, for
example the string (PAXEL) representations of condition / slot / repeat
expressions and the related vtable ids (for “punching” during expression compilation)
The spec of an expression invocation, the necessary configuration
for initializing a pointer to (or copy of, in some cases) the data behind a symbol.
For example, if an expression uses i, that i needs to be “invoked,” bound dynamically
to some data on the other side of i for the context of a particular expression. ExpressionSpecInvocation
holds the recipe for such an invocation, populated as a part of expression compilation.
Pulled from host Cargo.toml
Container for a parsed Literal object
Container for holding metadata about original Location in Pax Template
Used for source-mapping
Definition container for an entire Pax cartridge
These flags describe the aspects of properties that affect RIL codegen.
Properties are divided into modal axes (exactly one value should be true per axis per struct instance)
Codegen considers each element of the cartesian product of these axes
Represents an entry within a component template, e.g. a declaration inside a template
Each node in a template is represented by exactly one TemplateNodeDefinition, and this is a compile-time
concern. Note the difference between compile-time definitions and runtime instances.
A compile-time TemplateNodeDefinition corresponds to a single runtime RenderNode instance.
Container for parsed values with optional location information
Location is optional in case this token was generated dynamically
Describes metadata surrounding a property’s type, gathered from a combination of static & dynamic analysis